Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1976

reference: 209-tree-1
name: 1976
tree-preservation-order: undefined
209-tpo-1
uprn
address-text
point: POINT (-0.935418 50.866106)
geometry: MULTIPOLYGON (((-0.935361 50.866100,-0.935363 50.866111,-0.935371 50.866121,-0.935384 50.866129,-0.935399 50.866134,-0.935417 50.866136,-0.935434 50.866134,-0.935450 50.866130,-0.935463 50.866122,-0.935471 50.866112,-0.935474 50.866101,-0.935472 50.866089,-0.935464 50.866079,-0.935452 50.866071,-0.935436 50.866066,-0.935418 50.866064,-0.935401 50.866066,-0.935385 50.866071,-0.935372 50.866079,-0.935364 50.866089,-0.935361 50.866100)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL